[leancode_force_update] Upgrade in_app_update to ^5.0.0 - #562

Recovers the 10 points lost on pub.dev's Support up-to-date dependencies → All of the package dependencies are supported in the latest version check.

Cause

in_app_update was the only dependency behind. Per the live pana report:

Every other dependency already resolved to its latest version, so this one constraint accounted for the whole deduction.

Changes

in_app_update 5.0.0 has no Dart API changes — its changelog is only "migrate to Flutter's built-in Kotlin" (the plugin no longer applies the Kotlin Gradle Plugin or declares its classpath, and uses the kotlin { compilerOptions } DSL). Everything force_update_guard.dart uses — checkForUpdate, startFlexibleUpdate, completeFlexibleUpdate, performImmediateUpdate, AppUpdateInfo.immediateUpdateAllowed — is unchanged, so the package's own source needed no edits.

It does require Dart ^3.12.0 / Flutter >=3.44.0, so the environment constraints move up with it:

• pubspec.yaml: in_app_update: ^5.0.0, sdk: '>=3.12.0 <4.0.0', flutter: ">=3.44.0", version → 1.0.5-alpha
• leancode_force_update-test.yml: min-version matrix entry 3.38.x → 3.44.x (the publish workflow already pinned Dart 3.12 / Flutter 3.44.x and needed nothing)
• example/: SDK floor bumped, pubspec.lock regenerated

Example: private initializing formals

Raising the example's SDK floor also raises its language version, which made prefer_initializing_formals start firing on the old workaround idiom:

required ForceUpdateController forceUpdateController,
}) : _forceUpdateController = forceUpdateController;

Since Dart 3.12 a named initializing formal this._foo is passed by callers as foo, so the workaround is redundant and the lint flags it. Fixed via dart fix --apply (4 fixes across 3 files); call sites are unchanged. Without this, the bumped CI matrix would have gone red.

The regenerated example/pubspec.lock also picks up drift that was already stale on master — it still pinned leancode_contracts 0.9.0 and leancode_force_update 1.0.3-alpha.

Verification

Run locally on Flutter 3.44.0 / Dart 3.12.0 — deliberately the exact floor the pubspec now declares, rather than 3.44.x:

• flutter analyze → no issues
• flutter test → 8/8 passing
• flutter pub publish --dry-run → clean (only the standard "not an incremental update" hint that every -alpha release in this package triggers)
• pana → 160/160, with 10/10 points: All of the package dependencies are supported in the latest version

Out of scope

The example's Android toolchain is stale and untested here — android/build.gradle pins Kotlin 1.7.10 / AGP 7.3.0 with Gradle 7.5 in the legacy apply plugin layout. That was already incompatible with the Flutter floor this package declared before this PR, and nothing in CI builds the example APK, so modernizing it is left as separate work.

Generated by Claude Code